Data object aggregation to manage an order summary

ABSTRACT

Methods, systems, and devices supporting data storage are described. A database system may store order information for an organization. This order information may span multiple steps of an order lifecycle, including order creation, order changes, order fulfillment, etc. To efficiently store order information for low-latency querying and data consistency, the database system may implement order summaries. For example, a database server may receive a new order data object associated with an order identifier and may create a corresponding order summary data object. If the database system receives any additional data objects associated with the same order identifier, the database server may update the order summary data object based on the additional data objects. If the database system receives a query for information related to the order, the system may retrieve queried values directly from the order summary data object, rather than aggregating data on-the-fly across multiple underlying data objects.

FIELD OF TECHNOLOGY

The present disclosure relates generally to database systems and dataprocessing, and more specifically to data object aggregation to managean order summary.

BACKGROUND

A cloud platform (i.e., a computing platform for cloud computing) may beemployed by many users to store, manage, and process data using a sharednetwork of remote servers. Users may develop applications on the cloudplatform to handle the storage, management, and processing of data. Insome cases, the cloud platform may utilize a multi-tenant databasesystem. Users may access the cloud platform using various user devices(e.g., desktop computers, laptops, smartphones, tablets, or othercomputing systems, etc.).

In one example, the cloud platform may support customer relationshipmanagement (CRM) solutions. This may include support for sales, service,marketing, community, analytics, applications, and the Internet ofThings. A user may utilize the cloud platform to help manage contacts ofthe user. For example, managing contacts of the user may includeanalyzing data, storing and preparing communications, and trackingopportunities and sales.

Some cloud platforms supporting CRM solutions may store orderinformation for tenants of a database system. Maintaining orderinformation may pose multiple challenges, such as presenting orderinformation to a user in a digestible fashion, accurately andefficiently generating values related to the order, and efficientlystoring order-related information. In some systems, maintaining orderinformation may involve querying multiple data domains (e.g., multipledatabases, multiple application programming interfaces (APIs), multipleapplications, multiple clients, etc.) to retrieve and/or update orderrelated information. Querying multiple data domains may increase systemlatency and degrade user experience. In some cases, maintaining orderinformation without querying multiple data domains may create datainconsistencies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for cloud computing thatsupports data object aggregation to manage an order summary inaccordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a system that supports data objectaggregation to manage an order summary in accordance with aspects of thepresent disclosure.

FIG. 3 illustrates an example of a user device including a userinterface that supports data object aggregation to manage an ordersummary in accordance with aspects of the present disclosure.

FIG. 4 illustrates an example of an order lifecycle that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure.

FIG. 5 illustrates an example of a process flow that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure.

FIG. 6 shows a block diagram of an apparatus that supports data objectaggregation to manage an order summary in accordance with aspects of thepresent disclosure.

FIG. 7 shows a block diagram of a data aggregation manager that supportsdata object aggregation to manage an order summary in accordance withaspects of the present disclosure.

FIG. 8 shows a diagram of a system including a device that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure.

FIGS. 9 through 11 show flowcharts illustrating methods that supportdata object aggregation to manage an order summary in accordance withaspects of the present disclosure.

DETAILED DESCRIPTION

A database system may store order information for an organization. Thisorder information may include any data related to an agreement betweenthe organization and a user or other organization to provision servicesor deliver products. For example, the order information may span anumber of steps of an order lifecycle, including order creation, orderchanges, order fulfillment, shipping, payment, or any combination ofthese and other processes associated with an order. One or more of thedifferent steps in the order lifecycle may correspond to differentdomains (e.g., with different systems providing the data relevant tothat step). For example, the database system may receive order creationinformation from the organization, payment information from a bank,shipping information from a carrier, etc. The data associated with thesedifferent processes may be stored as different types of data objects, indifferent data formats, with different data fields, or a combinationthereof. In some cases, these data objects are stored as immutable dataobjects (e.g., within a transaction order) at the database system tomaintain data integrity. However, such an implementation for datastorage may result in significant processing latency when querying fororder information. For example, in response to a query, the databasesystem may retrieve data from multiple different data objects—in somecases, across different databases or domains—in order to aggregateinformation representing the full lifecycle of the order.

To efficiently store order information for low-latency querying and dataconsistency, the database system may implement order summaries. An ordersummary may track the current state of an order, automatically updatingas additional order information is received at the database system(e.g., across any number of systems or domains). For example, a databaseserver may receive a new order data object associated with an orderidentifier and may create a corresponding order summary data objectassociated with the order identifier. If the database system receivesany additional data objects associated with the same order identifier,the database server may update the order summary data object based onthe additional data objects. In some cases, the updating may involveaggregating fields across multiple data objects, replacing field valueswith updated field values, creating new field values based on newinformation, or any combination thereof. The order summary data objectmay additionally include references (e.g., links, pointers, etc.) to theunderlying data objects upon which the order summary data object isbased. In some cases, these underlying data objects may be stored asimmutable data objects in the database system to maintain dataintegrity, while the order summary data objects support modification inthe storage system.

The order summary data objects may support efficient querying of orderinformation. For example, because an order summary data object can tracka current state of an order, the database server may handle queries forinformation associated with the order using the order summary dataobject. That is, rather than querying multiple data objects andaggregating information on-the-fly in order to respond to a query, thedatabase server may retrieve a response to the query directly from theorder summary data object based on the order summary data objectcontaining aggregate information for multiple data objects associatedwith the order. Retrieving a value directly from an order summary dataobject may support low-latency querying, as the database server may notsearch for multiple different data objects across the database system.This efficient query handling may support real-time or pseudo-real-timeuser interface updates, as selections or changes made by a user in theuser interface may be handled by a single data object at the databasesystem (or by a single data object stored locally in memory of the userdevice displaying the user interface).

Additionally, as the database system automatically updates the ordersummary data object based on receiving new data objects associated withthe order, the user interface—that is based on the order summary dataobject—may also automatically update as the new data objects arereceived at the database system. This may allow the user interface todisplay, in a single view, up-to-date information for the current stateof an order. The order summary data objects may supportorganization-facing user interfaces, customer-facing user interfaces, orboth. Additionally or alternatively, the database system may be anexample of a multi-tenant database system and may store order summarydata objects for multiple different tenants.

Aspects of the disclosure are initially described in the context of anenvironment supporting an on-demand database service. Additional aspectsof the disclosure are described with reference to an order transactionsystem, a user device, an order lifecycle, and a data aggregationprocess flow. Aspects of the disclosure are further illustrated by anddescribed with reference to apparatus diagrams, system diagrams, andflowcharts that relate to data object aggregation to manage an ordersummary.

FIG. 1 illustrates an example of a system 100 for cloud computing thatsupports data object aggregation to manage an order summary inaccordance with aspects of the present disclosure. The system 100includes cloud clients 105, contacts 110, cloud platform 115, and datacenter 120. Cloud platform 115 may be an example of a public or privatecloud network. A cloud client 105 may access cloud platform 115 overnetwork connection 135. The network may implement transfer controlprotocol and internet protocol (TCP/IP), such as the Internet, or mayimplement other network protocols. A cloud client 105 may be an exampleof a user device, such as a server (e.g., cloud client 105-a), asmartphone (e.g., cloud client 105-b), or a laptop (e.g., cloud client105-c). In other examples, a cloud client 105 may be a desktop computer,a tablet, a sensor, or another computing device or system capable ofgenerating, analyzing, transmitting, or receiving communications. Insome examples, a cloud client 105 may be operated by a user that is partof a business, an enterprise, a non-profit, a startup, or any otherorganization type.

A cloud client 105 may interact with multiple contacts 110. Theinteractions 130 may include communications, opportunities, purchases,sales, or any other interaction between a cloud client 105 and a contact110. Data may be associated with the interactions 130. A cloud client105 may access cloud platform 115 to store, manage, and process the dataassociated with the interactions 130. In some cases, the cloud client105 may have an associated security or permission level. A cloud client105 may have access to certain applications, data, and databaseinformation within cloud platform 115 based on the associated securityor permission level and may not have access to others.

Contacts 110 may interact with the cloud client 105 in person or viaphone, email, web, text messages, mail, or any other appropriate form ofinteraction (e.g., interactions 130-a, 130-b, 130-c, and 130-d). Theinteraction 130 may be a business-to-business (B2B) interaction or abusiness-to-consumer (B2C) interaction. A contact 110 may also bereferred to as a customer, a potential customer, a lead, a client, orsome other suitable terminology. In some cases, the contact 110 may bean example of a user device, such as a server (e.g., contact 110-a), alaptop (e.g., contact 110-b), a smartphone (e.g., contact 110-c), or asensor (e.g., contact 110-d). In other cases, the contact 110 may beanother computing system. In some cases, the contact 110 may be operatedby a user or group of users. The user or group of users may beassociated with a business, a manufacturer, or any other appropriateorganization.

Cloud platform 115 may offer an on-demand database service to the cloudclient 105. In some cases, cloud platform 115 may be an example of amulti-tenant database system. In this case, cloud platform 115 may servemultiple cloud clients 105 with a single instance of software. However,other types of systems may be implemented, including—but not limitedto—client-server systems, mobile device systems, and mobile networksystems. In some cases, cloud platform 115 may support CRM solutions.This may include support for sales, service, marketing, community,analytics, applications, and the Internet of Things. Cloud platform 115may receive data associated with contact interactions 130 from the cloudclient 105 over network connection 135 and may store and analyze thedata. In some cases, cloud platform 115 may receive data directly froman interaction 130 between a contact 110 and the cloud client 105. Insome cases, the cloud client 105 may develop applications to run oncloud platform 115. Cloud platform 115 may be implemented using remoteservers. In some cases, the remote servers may be located at one or moredata centers 120.

Data center 120 may include multiple servers. The multiple servers maybe used for data storage, management, and processing. Data center 120may receive data from cloud platform 115 via connection 140, or directlyfrom the cloud client 105 or an interaction 130 between a contact 110and the cloud client 105. Data center 120 may utilize multipleredundancies for security purposes. In some cases, the data stored atdata center 120 may be backed up by copies of the data at a differentdata center (not pictured).

Subsystem 125 may include cloud clients 105, cloud platform 115, anddata center 120. In some cases, data processing may occur at any of thecomponents of subsystem 125, or at a combination of these components. Insome cases, servers may perform the data processing. The servers may bea cloud client 105 or located at data center 120.

The system 100 may support order management at a database system. Forexample, cloud clients 105 may store information related to ordersplaced by contacts 110 in the data center 120, the cloud platform 115,or both. This order information may originate from multiple differentdata domains associated with the full life cycle of an order (e.g.,including order creation, order modification, order fulfillment,shipping, payment, return requests, or any combination of these or otheroperations or actions related to an order placed by a user). The system100 may provide a summary of an order across the history of the orderand may combine the different actions that can happen to the order intoa usable view. The system 100 may present this view to a user (e.g., acloud client 105, a contact 110, etc.) in a user interface of a userdevice.

In some other systems, different applications, platforms, or databasesmay store order information across multiple data domains. In some cases,an order may include multiple data objects, and the multiple dataobjects may be stored in multiple different data domains. Orderinformation may be maintained through the creation of an original orderas well as one or more change orders. In some examples, each changeorder may be associated with the original order. Maintaining theoriginal order and the related change orders separately may increasesystem latency when calculating information related to an order. Forexample, to retrieve information related to the order (e.g.,incorporating multiple steps in the order history), information from theoriginal order as well as one or more subsequent change orders may bequeried to determine the order-related information. Querying multipledata objects, multiple data domains, or both may significantly increasethe processing latency associated with handling the query. Such latencymay impact the usability of a user interface displaying the orderinformation, especially for real-time or pseudo-real-time userinterfaces.

In contrast, the system 100 may implement order summary data objects tomanage orders. In some cases, order summaries may improve the efficiencyof generating and/or accessing information related to orders. In someexamples, order summaries may improve user experience. For example,order summaries may accurately and efficiently provide insights into acurrent state of an order. In some cases, an order summary may providean efficient way to extract and/or generate information related to anorder.

An order summary may maintain one or more order-related data fields. Insome cases, an order summary may be created when an order (e.g., anoriginal order associated with a particular order identifier) iscreated. In some examples, the order summary may be updated when anadditional data object related to the order (e.g., a change order, afulfillment order, a return order, etc.) is created or received.Accordingly, an order summary may include and/or be associated with oneor more database objects. For example, an order summary may beassociated with one or more tables, views, tuples, indexes, etc. In someexamples, an order summary may be identified and/or updated when achange order is received. For example, one or may fields included in anorder summary may be updated when a change order is received. In somecases, one or more fields of the order summary may be updated based onone or more existing values associated with the order summary and/or oneor more values associated with the change order. Updating an ordersummary may be performed in a constant asymptotic time complexity (e.g.,O(1)). For example, an amount of time associated with updating an ordersummary may not be affected by the number of change orders associatedwith an original order. In some cases, an original order may beassociated with numerous change orders.

Retrieving values associated with an order (e.g., a cost associated withan order, an amount of tax associated with an order, payment informationrelated to an order, coupons related to an order, shipping informationrelated to an order, account information related to an order, returnsrelated to an order, etc.) based on an order summary may decrease systemlatency, improve system efficiency, and improve user experience. Forexample, to query order-related information, the system may determinethe query results from the order summary data object, rather thanquerying multiple different underlying data objects that form thefoundation of the order summary data object.

It should be appreciated by a person skilled in the art that one or moreaspects of the disclosure may be implemented in a system 100 toadditionally or alternatively solve other problems than those describedabove. Furthermore, aspects of the disclosure may provide technicalimprovements to “conventional” systems or processes as described herein.However, the description and appended drawings only include exampletechnical improvements resulting from implementing aspects of thedisclosure, and accordingly do not represent all of the technicalimprovements provided within the scope of the claims.

FIG. 2 illustrates an example of a system 200 that supports data objectaggregation to manage an order summary in accordance with aspects of thepresent disclosure. The system 200, which may be an example of an ordertransaction system, includes a database server 205, a data store 210, anapplication server 215, a client 220 (e.g., associated with a clientdevice), a data store connection 225, an application server connection230, a client connection 235, an order summary store connection 245, anorder summary store 250, and a user device 255. The system 200 mayimplement aspects of the system 100 as described with reference toFIG. 1. For example, a database server 205, a data store 210, an ordersummary store 250, a data store connection 225, or a combination thereofmay be examples or components of a data center 120. An applicationserver 215, a client 220, an application server connection 230, a clientconnection 235, or a combination thereof may implement aspects ofsubsystem 125 as described with reference to FIG. 1.

The database server 205 may represent aspects of an application server,communication server, data processing server, database server,cloud-based server, server cluster, virtual machine, container, or somesimilar data processing device or system. The database server 205 maycommunicate with other devices such as the data store 210, theapplication server 215, the client 220, the order summary store 250, andthe user device 255. The data store 210 and/or the order summary store250 may implement various database ideologies (e.g., relational,non-relational, atomicity/consistency/isolation/durability (ACID),etc.). In some cases, the data store 210 and/or the order summary store250 may be relational databases (e.g., relational database managementsystems (RDBMSs)). Additionally or alternatively, the order summarystore 250 may be a component of the data store 210. The database server205 may use the data store connection 225 to receive data from and/ortransfer data to the data store 210. The database server 205 may use theapplication server connection 230 to receive data from and/or transferdata to the application server 215. The database server 205 may use theclient connection 235 to receive data from and/or transfer data to theclient 220 (e.g., a user device, a client application, a client server,etc.). The connections may be shared connections (e.g., connectionsallowing multiple users or processes to connect to a database), unsharedconnections (e.g., connections allowing a single user or process toconnect to a database), or a combination thereof. The connections mayimplement one or more security techniques to ensure that the securetransfer of tenant data.

In some cases, the database server 205 may create and/or identify anorder (e.g., an original order). This order may be a data objectincluding information related to an agreement between entities toprovision services or deliver products. The order may be referred to asa user order, a customer order, a business order, a client order, or anemployee order. In some cases, information related to the order may bestored in—or received from—multiple data domains (e.g., data store 210,one or more application servers 215, one or more clients 220, etc.). Forexample, order information may be queried or received via one or moreapplication programming interfaces (APIs) associated with differentsystems or domains. In some cases, one or more additional data objects(e.g., change orders, fulfillment orders, return orders, etc.) may beassociated with the order. In some examples, information related to theone or more additional orders may be stored in—or received from—multipledata domains. The information related to the one or more additionalorders may be stored in the same data domains as the order, differentdata domains than the order, overlapping data domains, or anycombination thereof.

In some cases, an order state (e.g., a current state) may reflect theoriginal order data object and all other data objects associated withthe original order. For example, one or more change orders may beassociated with an original order and may alter an order state. In somecases, the database server 205 may create an order summary data object240 when an original order is created. An order summary data object 240may reflect the current state of an order. In some examples, aspects ofthe order summary data object 240 may be read-only to a user. Forexample, order data contained in the order summary data object 240 maybe displayed as read-only data at a user interface. However, the orderdata may be updated based on received data objects associated with theorder.

In some examples, an order summary data object 240 may provide a summaryacross the history of an order. For example, the order summary dataobject 240 may combine different actions that can happen to an orderinto a usable view so that a user may be presented with an easy to useview of an order's current state. In some examples, an order summarydata object 240 may be presented as a single view that represents thecurrent state of an order (e.g., in a user interface of a user device255). In some examples, an order summary data object 240 may includefulfillment states, order changes, returns, or any combination thereof.In some cases, an order summary data object 240 may exist based on anoriginal order (i.e., an order data object including a new orderidentifier for which no data objects are currently stored at the datastore 210). The order summary data object 240 may inherit securitysetting, privacy settings, or both form the order data object. In somecases, additional data objects associated with the same order may updatethe security/privacy settings for the order summary data object 240.

The database server 205 may store an order summary data object 240 in anorder summary store 250. The database server 205 may use an ordersummary store connection 245 (e.g., a database connection) whenconnecting to the order summary store 250. In some examples, thedatabase server 205 may issue a database command (e.g., a query) to theorder summary store 250 over the order summary connection 245 to updatethe order summary store 250. In some examples, an original order may becreated at the application server 215, at the client 220, in response toan event at the application server 215, or in response to an event atthe client 220. Additionally, the application server 215 or client 220may create or trigger the creation of a change order (e.g., to cancel anitem, return an item, etc.) related to the original order. In someexamples, the data store 210 may store data objects representing theoriginal order and the change order. The database server 205 may createan order summary data object 240 based on the original order and mayupdate the order summary data object 240 based on the change order(e.g., if the original order and the change order are associated with asame order identifier). In this way, the order summary data object 240may be maintained based on stacks of transactional records.

In some cases, the database server 205 may query one or more datadomains (e.g., the data store 210, one or more application servers 215,one or more clients 220, etc.) to obtain information related to thestate of the order. However, these queries may be performed usingbackend processing to keep the state of the order summary data object240 up-to-date, rather than in response to a query for the current stateof the order summary data object 240. These different domains may storedata in different forms, in different formats, using different dataobjects, using different data object types, etc. The database server 205may convert information received from multiple domains into data formatssupported by the data store 210. Additionally, the converted informationmay support data aggregation from multiple different data objects and/ordata object types into the order summary data object 240. Theaggregation may involve calculating a field value at the order summarydata object 240 based on field values at the received data objects,creating a field value based on a field value at a received data object,replacing a field value based on a field value at a received dataobject, or some combination thereof. These fields may be default fieldsor custom fields and may exist in one or more of the received dataobjects or may be order summary-specific. The changes to the ordersummary data object 240 may be automatically triggered based on a newdata object associated with the same identifier, and the changes may beiterative (e.g., the database server 205 may not query previouslyreceived data objects associated with the same identifier to update theorder summary data object 240).

To store an order summary data object 240 that accurately reflects thecurrent state of an order, the database server 205 may perform one ormore data aggregation techniques. For example, the database server 205may perform functions, calculations, transformations, correlations,searches, or any combination thereof on information obtained from one ormore data domains to reflect the state of an order in the order summarydata object 240. As data objects are received or created at the databaseserver 205, the database server 205 may determine if the data objectsare associated with a specific order summary data object 240. Forexample, the order summary data object 240 may be associated with aparticular order identifier, and each associated data object (e.g.,change order data objects, fulfillment order data objects, payment dataobjects, etc.) may be associated with the same particular orderidentifier. As such, the database server 205 may automatically identifythe associated data objects and may update the order summary data object240 based on the associated data objects (e.g., in real-time orpseudo-real-time). This may allow the database server 205 to keep theorder summary data object 240 on disk and up-to-date with the currentstate of the order.

In some cases, the database server 205 may include the informationobtained from the one or more data domains, or information derived fromthe information obtained from the one or more data domains, in the ordersummary data object 240. In some cases, data objects associated with anorder summary data object 240 (e.g., change orders) may be indexed toimprove system performance. Additionally or alternatively, an ordersummary data object 240 may be referenced via a key (e.g., a foreignkey). In some cases, the order summary data object 240 may beconstructed and/or designed to improve system performance. For example,the order summary data object 240 may contain a primary key, one or moreforeign keys, or one or more indexes that support efficient querying. Insome examples, the order summary store 250 may be configured forreliable and/or efficient querying (e.g., based on transaction-basedquerying, one or more high bandwidth connections, proximity to thedatabase server 205, etc.).

In some cases, a user device 255 may communicate or otherwise interactwith the database server 205. In some examples, the user device 255 maydisplay information in a user interface based on an order summary dataobject 240. For example, the order summary data object 240 may containup-to-date information for the current state of an order, and the userdevice 255 may display some or all of the information stored in theorder summary data object 240. In some examples, the database server 205may transmit the order summary data object 240 to the user device 255.The user device 255 may display the user interface based on the ordersummary data object 240 stored in local memory at the user device 255(e.g., for low-latency, local querying). In some such examples, thedatabase server 205 may push updates of the order summary data object240 to the user device 255 (e.g., automatically or based on a userinput). Pushing order summary data object 240 updates to the user device255 may maintain up-to-date order summary information in the userinterface.

FIG. 3 illustrates an example of a user device 305 including a userinterface 310 that supports data object aggregation to manage an ordersummary in accordance with aspects of the present disclosure. In somecases, the user interface 310 may provide a single view that representsthe current state of an order. The user interface 310 may display dataassociated with an order summary data object corresponding to an orderidentifier. In some cases, the user interface 310 may additionallydisplay data associated with other data objects corresponding to theorder identifier and related to the order summary data object. Asillustrated, the user interface 310 may include an order summaryidentifier 345, order summary details 315, summary information 320(e.g., including an item list 365, shipping information 370, paymentinformation 375, etc.), order summary totals 325, contact details 330, aguided action list 335 (e.g., including add 350, cancel 355, discount360, or some combination of these or other supported actions), andrelated quick links 340. However, it is to be understood that the userinterface 310 represents an example user interface, and other userinterface configurations are supported by the techniques and processesdescribed herein.

The user interface 310 may support order summaries as described withreference to FIGS. 1 and 2. In some cases, a user may view and interactwith the user interface 310 to understand an order and various aspectsof the order. For example, the user may use the user interface 310 toanswer questions such as “what items have been cancelled?”, “what itemscan be cancelled?”, “what items have been allocated?”, “what items canbe allocated?”, “what items have been fulfilled?”, “what items can befulfilled?”, “what items have been returned?”, “what items can bereturned?”, “what items have been invoiced?”, etc. In some examples, auser may use the user interface 310 to understand the current state ofan order. For example, because the user interface 310 displays data froman order summary that tracks any changes to an order, the user interface310 can display the current state of an order including any ordermodifications following the order creation based on a single source(i.e., the order summary data object). For examples, the user interface310 may display information such as price changes, discounts, shippingaddresses, shipping methods, items added, etc. for an order.

The user interface 310 may display information for an order based on theorder summary data object created and maintained for that order. Theorder summary identifier 345 may display the identifying value (i.e.,the order identifier) associated with the order. This order identifiermay be unique for the order summary data object, where no other ordersummary data objects include the same order identifier. If the databasesystem receives data objects including the same order identifier, thedatabase system may automatically determine to update the order summarydata object based on the received data objects due to the shared orderidentifier.

In some cases, the order summary details 315 may display orderinformation such as an account name, an order date, a sales channel, achannel type, an order status, or a billing address. In some examples,the order summary details 315 may be used as a high-level summary of theorders, including information that is not specific to any particularitem in the order. The summary information 320 may display informationrelated to one or more items within an order. In some examples, thesummary information 320 may include multiple selectable tabs. Themultiple tabs may include a summary tab, a related tab, a details tab,or some combination of these or other tabs. In some cases, the summaryinformation 320 may display product details for an item list 365,shipping information 370, payment information 375, or a combinationthereof. For example, product details may include information related toone or more items in the order, such as a description and/or a number, astatus (e.g., ordered, fulfilled, shipped, returned, backordered, etc.),quantity, unit price, adjustment, tax, item total, etc. Shippinginformation 370 may include information related to shipping such asname, address, shipping method, etc. Payment information 375 may includeinformation related to payments such as method, name, authorized amount,captured amount, etc.

In some cases, the order summary totals 325 may provide informationrelated to the costs of an order. For example, the order summary totals325 may include fields such as subtotal, adjustments, shipping, tax,total, etc. Additionally or alternatively, the order summary totals 325may provide information related to returns such as refunds, exchanges,etc. The values displayed in the order summary totals 325 may beretrieved directly from the order summary data object but may be basedon multiple different data objects. For example, the database system mayreceive an order data object and a number of change order data objectsand may update fields in the order summary data object representing theorder summary totals 325 based on the order data object and the changeorder data objects. As such, the values in the order summary totals 325may not be present in any one order data object or change order dataobject. Instead, based on a data aggregation process across these dataobjects, the order summary data object may store these values. This mayallow a user to tag (e.g., assign a value or flag to) one or more ofthese values, and the database system may represent this tag in theunderlying data based on creating, maintaining, and storing the ordersummary data object with these values.

In some cases, the contact details 330 may provide contact informationrelated to the order. For example, the contact details 330 may displaycontact information such as a name, email, phone number, or combinationthereof for a user associated with an account that placed the order.Additionally or alternatively, the contact details 330 may displaycontact information for a person or user that is not associated with theaccount that placed the order.

In some cases, the guided action list 335 may provide multipleselectable tabs. For example, the guided action list 335 may provide anactions tab and a history tab. In some cases, the guided action list 335may allow one or more items to be added to an order (via an add 350action). In some other cases, the guided action list 335 may allow oneor more items of an order to be canceled (e.g., via a cancel 355action). In yet some other cases, the guided action list 335 may allowone or more items of an order to be discounted (e.g., via a discount 360action). In some examples, the guided actions list 335 may display ahistory of actions associated with an order. For example, the guidedactions list 335 may display items that have been added to an order,items that have been canceled from an order, or items that have beendiscounted on an order. Additionally or alternatively, the guidedactions list 335 may be filterable and allow current actions and/or pastactions to be filtered based on various criteria. For example, theactions may be filtered based on a date, a time, a date range, a timerange, a type of action, an item quantity or quality, a user associatedwith an order, or any combination thereof.

In some cases, the related quick links 340 may provide links related toone or more orders. These links may allow a user to view or access oneor more of the data objects associated with the order summary dataobject. For example, the related quick links 340 may link to theoriginal order, change orders, fulfillment orders, return orders,payments, shipping notifications, etc. In a specific example, therelated quick links 340 may provide a fulfillment orders link. Forexample, the fulfillment orders link may allow a user to view one ormore fulfillment orders related to the order. In some cases, allfulfillment orders associated with the order may be displayed when thefulfillment orders link is selected. The fulfillment orders link maydisplay a numeric value representing how many fulfillment orders areassociated with the order. In some cases, the fulfillment orders linkmay display a visual indication of whether or not there are fulfillmentorders associated with the order. In another example, the related quicklinks 340 may provide a payments link. For example, the payments linkmay allow a user to view one or more payments related to the order. Insome cases, all payments associated with the order may be displayed whenthe payments link is selected. The payments link may display a numericvalue representing how many payments are associated with the order. Insome cases, the payments link may display a visual indication of whetheror not there are payments associated with the order.

In some cases, the user interface 310 may support user login and/or useraccount creation. In some examples, the user interface 310 may displayinformation that a user has permission to view and may hide (orotherwise refrain from displaying) other information. For example, theuser interface 310 may display information related to orders that werecreated by the logged in user. Some database systems may supportmultiple different user interfaces for displaying order summaryinformation. For example, a system may support a first user interfacefor an administrative user at an organization fulfilling the order and asecond user interface for a customer placing the order. The databasesystem may automatically filter the information that may be viewed ineach user interface according to the role of the user viewing the userinterface. Additionally or alternatively, the database system maysupport customizable views for users.

FIG. 4 illustrates an example of an order lifecycle 400 that supportsdata object aggregation to manage an order summary in accordance withaspects of the present disclosure. In some cases, the order lifecycle400 may represent one or more events related to an order. For example,the order lifecycle 400 may include an order creation event 405, achange order event 410, a first fulfillment order initiation 415, asecond fulfillment order initiation 420, a fulfillment completion event425, and a return item event 430. However, it is to be understood thatan order lifecycle 400 may involve any combination of these or otherrelevant events in any sequence.

In some cases, an order summary may be created based on an ordercreation event 405. For example, the creation of an order summary may betriggered by an order creation event 405. In some cases, an ordercreation event 405 may occur based on a user placing an order. In somecases, an order summary may be updated based on a change order event410. A change order event 410 may occur based on a user canceling anitem in a previously placed order, selecting a new item in a previouslyplaced order, or modifying any other details associated with apreviously placed order.

In some cases, a first fulfillment order initiation 415 may occur basedon the start and/or completion of an action taken to fulfill the order.For example, a first fulfillment order initiation 415 may be triggeredwhen one or more items of an order are retrieved from a warehouse,packaged for shipping, sent to a shipping service, etc. In some cases, asecond fulfillment order initiation 420 may occur based on the startand/or completion of an action taken to fulfill the order. For example,a second fulfillment order initiation 420 may be triggered when one ormore items of the order are retrieved from a warehouse, packaged forshipping, sent to a shipping service, etc. As illustrated, a fulfillmentorder may correspond to a subset of the items in an order. For example,based on item availabilities, different warehouses, shipping services,etc., different portions of an order may be fulfilled at differenttimes. In some cases, a fulfillment completion event 425 may occur basedon the fulfillment of all items related to an order. The fulfillmentcompletion event 425 may trigger a change to the status of an ordersummary. For example, the fulfillment completion event 425 may switch anorder status field from “Open” to “Closed” in the order summary dataobject. In some cases, a return item event 430 may occur based on thereturn of one or more items related to an order. Such an event mayfurther update the status of the order summary (e.g., switching theorder status field from “Closed” to “Open.”

FIG. 5 illustrates an example of a process flow 500 that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure. The process flow 500 includes a databaseserver 505, a data store 510 associated with the database server 505, auser device 515, and one or more systems 520 associated with one or moredomains. These may be examples of the corresponding devices describedwith reference to FIGS. 1 through 4. The database server 505 maygenerate and update an order summary in the data store 510. In somecases, a user device 515 may query the database system (e.g., thedatabase server 505, the data store 510, or both) for informationrelated to the order summary. For example, the user device 515 may querythe database system for order data to display in a user interface.Alternative examples of the following may be implemented, where somesteps are performed in a different order than described or are notperformed at all. In some cases, steps may include additional featuresnot mentioned below, or further steps may be added.

At 525, the database server 505 may receive an order data object from asystem 520. For example, the system 520 may be an application, an API, auser device, a database, etc. In some cases, the order data object mayinclude an order identifier (e.g., a number, a set of characters, etc.).In some cases, the database server 505 may receive the order data objectbased on the creation of an order (e.g., an original order).

At 530, the database server 505 may create an order summary (e.g., anorder summary data object). The database server 505 may create the ordersummary data object based on receiving the order data object. In somecases, the database server 505 may store the order summary data objectin a data store 510. In some examples, the data store 510 may be arelational database or a non-relational database. The order summary dataobject may include information related to a current state associatedwith the order identifier. In some cases, the database server 505 maydetermine that the data store 510 does not contain an existing ordersummary data object corresponding to the order identifier and may createthe order summary data object based on the determination that data store510 does not contain an existing order summary corresponding to theorder identifier. In some cases, the database server 505 may create orupdate a key (e.g., a foreign key) of the order data object. In somecases, the key may reference a key (e.g., a primary key) of the ordersummary data object.

At 535, the database server 505 may receive an additional data object.In some cases, the additional data object may be associated with theorder identifier. In some cases, the additional data object may bestored with a primary key and a foreign key referencing another dataobject (e.g., an order data object). The database server 505 may receivethe additional data object from a system 520, where the order dataobject and the additional data object may be received from differentsystems 520 (or different domains).

At 540, the database server 505 may update the order summary dataobject. For example, the database server 505 may update the ordersummary data object based on the additional data object. In some cases,the database server 505 may create or update one or more keys associatedwith the order summary data object. For example, the database server 505may create or update a key (e.g., a foreign key) of the order summarydata object. In some cases, the key may reference a key (e.g., a primarykey) of the additional data object, the order data object, or both. Thatis, a first reference of the order summary data object may reference theorder data object and a second reference of the order summary dataobject may reference the additional data object. The database server 505may additionally or alternatively aggregate information from theadditional data object with information already stored for the ordersummary (e.g., based on the order data object) to update field valuesstored for the order summary data object.

At 545, the database server 505 may receive a query. In some cases, thequery may be for a value corresponding to a first field value associatedwith the order data object and a second field value associated with theadditional data object. The query may include the order identifier. Insome cases, the query may be based on a user selection at a user device515 initiating a query. In some cases, the query may be initiated from auser interface, such as user interface 310 as described with referenceto FIG. 3.

At 550, the database server 505 may retrieve the value directly from theupdated order summary data object in response to the query. For example,rather than aggregating information from the order data object and theadditional data object on-the-fly to handle the query, the databaseserver 505 may handle the query using a stored value at the updatedorder summary data object. By handling the query using a single dataobject (i.e., the order summary data object) rather than multiple dataobjects, the database server 505 may reduce the latency involved inupdating an order summary user interface. This may support a real-timeuser interface, where a real-time time constraint associated withreal-time applications may be met by the low-latency query handling(e.g., based on the order summary data object). In some cases, the valuemay be retrieved from the updated order summary data object based on theupdated order summary data object including information for both theorder data object and the additional data object. At 555, the databaseserver 505 may send a query response to the user device 515 including atleast the value retrieved from the updated order summary data object.

FIG. 6 shows a block diagram 600 of an apparatus 605 that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure. The apparatus 605 may include an input module610, a data aggregation manager 615, and an output module 645. Theapparatus 605 may also include a processor. Each of these components maybe in communication with one another (e.g., via one or more buses). Insome cases, the apparatus 605 may be an example of a user terminal, adatabase server, or a system containing multiple computing devices.

The input module 610 may manage input signals for the apparatus 605. Forexample, the input module 610 may identify input signals based on aninteraction with a modem, a keyboard, a mouse, a touchscreen, or asimilar device. These input signals may be associated with user input orprocessing at other components or devices. In some cases, the inputmodule 610 may utilize an operating system such as iOS®, ANDROID®,MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operatingsystem to handle input signals. The input module 610 may send aspects ofthese input signals to other components of the apparatus 605 forprocessing. For example, the input module 610 may transmit input signalsto the data aggregation manager 615 to support data object aggregationto manage an order summary. In some cases, the input module 610 may be acomponent of an input/output (I/O) controller 815 as described withreference to FIG. 8.

The data aggregation manager 615 may include a data object receptioncomponent 620, an order summary creation component 625, an order summaryupdating component 630, a query reception component 635, and an ordersummary retrieval component 640. The data aggregation manager 615 may bean example of aspects of the data aggregation manager 705 or 810described with reference to FIGS. 7 and 8.

The data aggregation manager 615 and/or at least some of its varioussub-components may be implemented in hardware, software executed by aprocessor, firmware, or any combination thereof. If implemented insoftware executed by a processor, the functions of the data aggregationmanager 615 and/or at least some of its various sub-components may beexecuted by a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described in thepresent disclosure. The data aggregation manager 615 and/or at leastsome of its various sub-components may be physically located at variouspositions, including being distributed such that portions of functionsare implemented at different physical locations by one or more physicaldevices. In some examples, the data aggregation manager 615 and/or atleast some of its various sub-components may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In other examples, the data aggregation manager 615 and/or at least someof its various sub-components may be combined with one or more otherhardware components, including but not limited to an I/O component, atransceiver, a network server, another computing device, one or moreother components described in the present disclosure, or a combinationthereof in accordance with various aspects of the present disclosure.

The data aggregation manager 615 may be implemented at a server (e.g., adatabase server, an application server, a server cluster, a virtualmachine, a container, etc.) of a database system. The data objectreception component 620 may receive an order data object including anorder identifier. The order summary creation component 625 may create anorder summary data object based on receiving the order data object.

Furthermore, the data object reception component 620 may receive anadditional data object associated with the order identifier. The ordersummary updating component 630 may update the order summary data objectbased on the additional data object.

The query reception component 635 may receive a query for a valuecorresponding to a first field value at the order data object and asecond field value at the additional data object, where the queryincludes the order identifier. The order summary retrieval component 640may retrieve, in response to the query, the value directly from theupdated order summary data object based on the updated order summarydata object including information for both the order data object and theadditional data object.

The output module 645 may manage output signals for the apparatus 605.For example, the output module 645 may receive signals from othercomponents of the apparatus 605, such as the data aggregation manager615, and may transmit these signals to other components or devices. Insome specific examples, the output module 645 may transmit outputsignals for display in a user interface, for storage in a database ordata store, for further processing at a server or server cluster, or forany other processes at any number of devices or systems. In some cases,the output module 645 may be a component of an I/O controller 815 asdescribed with reference to FIG. 8.

FIG. 7 shows a block diagram 700 of a data aggregation manager 705 thatsupports data object aggregation to manage an order summary inaccordance with aspects of the present disclosure. The data aggregationmanager 705 may be an example of aspects of a data aggregation manager615 or a data aggregation manager 810 described herein. The dataaggregation manager 705 may include a data object reception component710, an order summary creation component 715, an order summary updatingcomponent 720, a query reception component 725, an order summaryretrieval component 730, a storage component 735, a field aggregationcomponent 740, a tagging component 745, a multi-system component 750, adisplay component 755, a data object retrieval component 760, an ordersummary ramp up component 765, or any combination of these or othercomponents for order summary management. Each of these modules maycommunicate, directly or indirectly, with one another (e.g., via one ormore buses).

The data aggregation manager 705 may support data object aggregation ata database system. The data object reception component 710 may receivean order data object including an order identifier. The order summarycreation component 715 may create an order summary data object based onreceiving the order data object. In some cases, the order summary dataobject inherits field-based security parameters from the order dataobject. Additionally or alternatively, in some examples, the ordersummary creation component 715 may determine, upon receiving the orderdata object, that the database system does not currently store anexisting order summary data object corresponding to the orderidentifier, where the order summary data object is created based on thedetermining that the database system does not currently store theexisting order summary data object.

The data object reception component 710 may receive an additional dataobject associated with the order identifier. The order summary updatingcomponent 720 may update the order summary data object based on theadditional data object. In some examples, the order summary updatingcomponent 720 may determine, upon receiving the additional data object,that the database system currently stores the order summary data objectcorresponding to the order identifier, where the order summary dataobject is updated based on the determining that the database systemcurrently stores the order summary data object.

In some cases, the additional data object may be an additional orderdata object, a change order data object, a fulfillment order dataobject, or a return order data object. In some cases, the additionaldata object is an additional order data object associated with the orderidentifier and the updating includes replacing current order informationfor the order summary data object including first order informationassociated with the order data object with second order informationassociated with the additional order data object. In some other cases,the additional data object is a change order data object associated withthe order identifier and the updating includes modifying the currentorder information for the order summary data object from the first orderinformation associated with the order data object based on third orderinformation associated with the change order data object. In yet someother cases, the additional data object is a fulfillment order dataobject associated with the order identifier or a return order dataobject associated with the order identifier and the updating includesmodifying a current status for at least one item in the order summarydata object based on the fulfillment order data object or the returnorder data object.

The query reception component 725 may receive a query for a valuecorresponding to a first field value at the order data object and asecond field value at the additional data object, where the queryincludes the order identifier. The order summary retrieval component 730may retrieve, in response to the query, the value directly from theupdated order summary data object based on the updated order summarydata object including information for both the order data object and theadditional data object.

The storage component 735 may store the order summary data object at thedatabase system. For example, the order summary data object may bestored on disk in a database (or stored in local memory, for example, ata user device), rather than calculated on-the-fly. In some cases, theorder summary data object may include a current state associated withthe order identifier. In some examples, the storage component 735 mayadditionally store the order data object and the additional data objectat the database system, where the order summary data object includes afirst indicator referencing the order data object and a second indicatorreferencing the additional data object.

The field aggregation component 740 may generate an initial value for anaggregate data field of the order summary data object based on the firstfield value for the order data object and may calculate the value forthe aggregate data field of the order summary data object based on thesecond field value for the additional data object, where the value isretrieved directly from the updated order summary data object based onthe calculating.

The tagging component 745 may receive a tag for the value (e.g., basedon a user input to a user interface). In some examples, the taggingcomponent 745 may tag the aggregate data field with the tag based on theorder summary data object including the value for the aggregate datafield, where the order data object and the additional data object do notinclude the value for tagging. In this way, the database system may taga current state value at the order summary data object, even if thiscurrent state value does not exist elsewhere in the underlying dataobjects excluding the order summary data object.

The multi-system component 750 may receive first informationcorresponding to the order data object via a first API for a firstsystem, where receiving the order data object includes generating theorder data object based on the first information. The multi-systemcomponent 750 may additionally receive second information correspondingto the additional data object via a second API different from the firstAPI for a second system different from the first system, where receivingthe additional data object includes generating the additional dataobject based on the second information. In some cases, the first fieldvalue is represented in the first information using a first data format,the second field value is represented in the second information using asecond data format different from the first data format, and the valueis represented in the updated order summary data object using the firstdata format, the second data format, or a third data format differentfrom the first data format and the second data format based onconverting the first data format to a first converted data format forthe order data object, converting the second data format to a secondconverted data format for the additional data object, or both.

The display component 755 may transmit, for display in a user interface,a set of data associated with the order summary data object, where thequery is received based on a user input to the user interface. In someexamples, the display component 755 may transmit, for display in theuser interface, the retrieved value in response to the query, where theuser interface is updated within a real-time time constraint based onretrieving the value directly from the updated order summary dataobject. In some cases, the user interface is associated with a tenant ofthe database system, an end-user for the tenant, or both.

In some examples, the query reception component 725 may receive anadditional query for an additional value corresponding to a third fieldvalue at the order data object, where the additional query includes theorder identifier. The data object retrieval component 760 may determinethat the order summary data object does not include the additional valueand may retrieve, in response to the additional query, the additionalvalue from the order data object based on the order summary data objectnot including the additional value.

The order summary ramp up component 765 may activate order summaries atthe database system. In some examples, the order summary ramp upcomponent 765 may identify an additional order data object including anadditional order identifier stored at the database system, may searchthe database system for one or more additional data objects associatedwith the additional order identifier, and may build an additional ordersummary data object corresponding to the additional order identifierbased on the additional order data object including the additional orderidentifier and the one or more additional data objects associated withthe additional order identifier. Such processes may be performed whenorder summaries are turned on for a system. That is, the system maybuild the corresponding order summary data objects based on informationcurrently stored at the database system (e.g., using backgroundprocesses, synchronous or asynchronous processing, etc.). Following rampup, the database system may create further order summary data objectsbased on new order data objects received at the system (e.g., ratherthan order data objects currently stored at the system).

FIG. 8 shows a diagram of a system 800 including a device 805 thatsupports data object aggregation to manage an order summary inaccordance with aspects of the present disclosure. The device 805 may bean example of or include the components of a database server or anapparatus 605 as described herein. The device 805 may include componentsfor bi-directional data communications including components fortransmitting and receiving communications, including a data aggregationmanager 810, an I/O controller 815, a database controller 820, memory825, a processor 830, and a database 835. These components may be inelectronic communication via one or more buses (e.g., bus 840).

The data aggregation manager 810 may be an example of a data aggregationmanager 615 or 705 as described herein. For example, the dataaggregation manager 810 may perform any of the methods or processesdescribed above with reference to FIGS. 6 and 7. In some cases, the dataaggregation manager 810 may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof.

The I/O controller 815 may manage input signals 845 and output signals850 for the device 805. The I/O controller 815 may also manageperipherals not integrated into the device 805. In some cases, the I/Ocontroller 815 may represent a physical connection or port to anexternal peripheral. In some cases, the I/O controller 815 may utilizean operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®,UNIX®, LINUX®, or another known operating system. In other cases, theI/O controller 815 may represent or interact with a modem, a keyboard, amouse, a touchscreen, or a similar device. In some cases, the I/Ocontroller 815 may be implemented as part of a processor. In some cases,a user may interact with the device 805 via the I/O controller 815 orvia hardware components controlled by the I/O controller 815.

The database controller 820 may manage data storage and processing in adatabase 835. In some cases, a user may interact with the databasecontroller 820. In other cases, the database controller 820 may operateautomatically without user interaction. The database 835 may be anexample of a single database, a distributed database, multipledistributed databases, a data store, a data lake, or an emergency backupdatabase.

Memory 825 may include random-access memory (RAM) and read-only memory(ROM). The memory 825 may store computer-readable, computer-executablesoftware including instructions that, when executed, cause the processorto perform various functions described herein. In some cases, the memory825 may contain, among other things, a basic I/O system (BIOS) which maycontrol basic hardware or software operation such as the interactionwith peripheral components or devices.

The processor 830 may include an intelligent hardware device (e.g., ageneral-purpose processor, a DSP, a central processing unit (CPU), amicrocontroller, an ASIC, an FPGA, a programmable logic device, adiscrete gate or transistor logic component, a discrete hardwarecomponent, or any combination thereof). In some cases, the processor 830may be configured to operate a memory array using a memory controller.In other cases, a memory controller may be integrated into the processor830. The processor 830 may be configured to execute computer-readableinstructions stored in a memory 825 to perform various functions (e.g.,functions or tasks supporting data object aggregation to manage an ordersummary).

FIG. 9 shows a flowchart illustrating a method 900 that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure. The operations of method 900 may beimplemented by a database server or its components as described herein.For example, the operations of method 900 may be performed by a dataaggregation manager as described with reference to FIGS. 6 through 8. Insome examples, a database server may execute a set of instructions tocontrol the functional elements of the database server to perform thefunctions described below. Additionally or alternatively, a databaseserver may perform aspects of the functions described below usingspecial-purpose hardware.

At 905, the database server may receive an order data object includingan order identifier. The operations of 905 may be performed according tothe methods described herein. In some examples, aspects of theoperations of 905 may be performed by a data object reception componentas described with reference to FIGS. 6 through 8.

At 910, the database server may create an order summary data objectbased on receiving the order data object. The operations of 910 may beperformed according to the methods described herein. In some examples,aspects of the operations of 910 may be performed by an order summarycreation component as described with reference to FIGS. 6 through 8.

At 915, the database server may receive an additional data objectassociated with the order identifier. The operations of 915 may beperformed according to the methods described herein. In some examples,aspects of the operations of 915 may be performed by a data objectreception component as described with reference to FIGS. 6 through 8.

At 920, the database server may update the order summary data objectbased on the additional data object. The operations of 920 may beperformed according to the methods described herein. In some examples,aspects of the operations of 920 may be performed by an order summaryupdating component as described with reference to FIGS. 6 through 8.

At 925, the database server may receive a query for a valuecorresponding to a first field value at the order data object and asecond field value at the additional data object, where the queryincludes the order identifier. The operations of 925 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 925 may be performed by a query reception component asdescribed with reference to FIGS. 6 through 8.

At 930, the database server may retrieve, in response to the query, thevalue directly from the updated order summary data object based on theupdated order summary data object including information for both theorder data object and the additional data object. The operations of 930may be performed according to the methods described herein. In someexamples, aspects of the operations of 930 may be performed by an ordersummary retrieval component as described with reference to FIGS. 6through 8.

FIG. 10 shows a flowchart illustrating a method 1000 that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure. The operations of method 1000 may beimplemented by a database server or its components as described herein.For example, the operations of method 1000 may be performed by a dataaggregation manager as described with reference to FIGS. 6 through 8. Insome examples, a database server may execute a set of instructions tocontrol the functional elements of the database server to perform thefunctions described below. Additionally or alternatively, a databaseserver may perform aspects of the functions described below usingspecial-purpose hardware.

At 1005, the database server (e.g., a database server at a databasesystem) may receive an order data object including an order identifier.The operations of 1005 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1005may be performed by a data object reception component as described withreference to FIGS. 6 through 8.

At 1010, the database server may determine, upon receiving the orderdata object, that the database system does not currently store anexisting order summary data object corresponding to the orderidentifier. The operations of 1010 may be performed according to themethods described herein. In some examples, aspects of the operations of1010 may be performed by an order summary creation component asdescribed with reference to FIGS. 6 through 8.

At 1015, the database server may create an order summary data objectbased on receiving the order data object, where the order summary dataobject is created based on the determining that the database system doesnot currently store the existing order summary data object. Theoperations of 1015 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1015 may beperformed by an order summary creation component as described withreference to FIGS. 6 through 8.

At 1020, the database server may receive an additional data objectassociated with the order identifier. The operations of 1020 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1020 may be performed by a data objectreception component as described with reference to FIGS. 6 through 8.

At 1025, the database server may determine, upon receiving theadditional data object, that the database system currently stores theorder summary data object corresponding to the order identifier. Theoperations of 1025 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1025 may beperformed by an order summary updating component as described withreference to FIGS. 6 through 8.

At 1030, the database server may update the order summary data objectbased on the additional data object, where the order summary data objectis updated based on the determining that the database system currentlystores the order summary data object. The operations of 1030 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1030 may be performed by an order summaryupdating component as described with reference to FIGS. 6 through 8.

At 1035, the database server may receive a query for a valuecorresponding to a first field value at the order data object and asecond field value at the additional data object, where the queryincludes the order identifier. The operations of 1035 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1035 may be performed by a query reception componentas described with reference to FIGS. 6 through 8.

At 1040, the database server may retrieve, in response to the query, thevalue directly from the updated order summary data object based on theupdated order summary data object including information for both theorder data object and the additional data object. The operations of 1040may be performed according to the methods described herein. In someexamples, aspects of the operations of 1040 may be performed by an ordersummary retrieval component as described with reference to FIGS. 6through 8.

FIG. 11 shows a flowchart illustrating a method 1100 that supports dataobject aggregation to manage an order summary in accordance with aspectsof the present disclosure. The operations of method 1100 may beimplemented by a database server or its components as described herein.For example, the operations of method 1100 may be performed by a dataaggregation manager as described with reference to FIGS. 6 through 8. Insome examples, a database server may execute a set of instructions tocontrol the functional elements of the database server to perform thefunctions described below. Additionally or alternatively, a databaseserver may perform aspects of the functions described below usingspecial-purpose hardware.

At 1105, the database server may receive first information correspondingto an order data object via a first API for a first system. Theoperations of 1105 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1105 may beperformed by a multi-system component as described with reference toFIGS. 6 through 8.

At 1110, the database server may generate the order data objectincluding an order identifier based on the first information. Theoperations of 1110 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1110 may beperformed by a data object reception component as described withreference to FIGS. 6 through 8.

At 1115, the database server may create an order summary data objectbased on the order data object. The operations of 1115 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1115 may be performed by an order summary creationcomponent as described with reference to FIGS. 6 through 8.

At 1120, the database server may receive second informationcorresponding to an additional data object via a second API differentfrom the first API for a second system different from the first system.The operations of 1120 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1120may be performed by a multi-system component as described with referenceto FIGS. 6 through 8.

At 1125, the database server may generate the additional data objectassociated with the order identifier based on the second information.The operations of 1125 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1125may be performed by a data object reception component as described withreference to FIGS. 6 through 8.

At 1130, the database server may update the order summary data objectbased on the additional data object. The operations of 1130 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1130 may be performed by an order summaryupdating component as described with reference to FIGS. 6 through 8.

A method for data object aggregation at a database system is described.The method may include receiving an order data object including an orderidentifier, creating an order summary data object based on receiving theorder data object, receiving an additional data object associated withthe order identifier, updating the order summary data object based onthe additional data object, receiving a query for a value correspondingto a first field value at the order data object and a second field valueat the additional data object, where the query includes the orderidentifier, and retrieving, in response to the query, the value directlyfrom the updated order summary data object based on the updated ordersummary data object including information for both the order data objectand the additional data object.

An apparatus for data object aggregation at a database system isdescribed. The apparatus may include a processor, memory coupled withthe processor, and instructions stored in the memory. The instructionsmay be executable by the processor to cause the apparatus to receive anorder data object including an order identifier, create an order summarydata object based on receiving the order data object, receive anadditional data object associated with the order identifier, update theorder summary data object based on the additional data object, receive aquery for a value corresponding to a first field value at the order dataobject and a second field value at the additional data object, where thequery includes the order identifier, and retrieve, in response to thequery, the value directly from the updated order summary data objectbased on the updated order summary data object including information forboth the order data object and the additional data object.

Another apparatus for data object aggregation at a database system isdescribed. The apparatus may include means for receiving an order dataobject including an order identifier, creating an order summary dataobject based on receiving the order data object, receiving an additionaldata object associated with the order identifier, updating the ordersummary data object based on the additional data object, receiving aquery for a value corresponding to a first field value at the order dataobject and a second field value at the additional data object, where thequery includes the order identifier, and retrieving, in response to thequery, the value directly from the updated order summary data objectbased on the updated order summary data object including information forboth the order data object and the additional data object.

A non-transitory computer-readable medium storing code for data objectaggregation at a database system is described. The code may includeinstructions executable by a processor to receive an order data objectincluding an order identifier, create an order summary data object basedon receiving the order data object, receive an additional data objectassociated with the order identifier, update the order summary dataobject based on the additional data object, receive a query for a valuecorresponding to a first field value at the order data object and asecond field value at the additional data object, where the queryincludes the order identifier, and retrieve, in response to the query,the value directly from the updated order summary data object based onthe updated order summary data object including information for both theorder data object and the additional data object.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the order summary data objectmay include a current state associated with the order identifier. Someexamples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for storing the ordersummary data object at the database system.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for storing the order dataobject and the additional data object at the database system, where theorder summary data object includes a first indicator referencing theorder data object and a second indicator referencing the additional dataobject.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining, uponreceiving the order data object, that the database system does notcurrently store an existing order summary data object corresponding tothe order identifier, where the order summary data object may be createdbased on the determining that the database system does not currentlystore the existing order summary data object.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining, uponreceiving the additional data object, that the database system currentlystores the order summary data object corresponding to the orderidentifier, where the order summary data object may be updated based onthe determining that the database system currently stores the ordersummary data object.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for generating an initialvalue for an aggregate data field of the order summary data object basedon the first field value for the order data object and calculating thevalue for the aggregate data field of the order summary data objectbased on the second field value for the additional data object, wherethe value may be retrieved directly from the updated order summary dataobject based on the calculating.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving a tag for thevalue and tagging the aggregate data field with the tag based on theorder summary data object including the value for the aggregate datafield, where the order data object and the additional data object do notinclude the value for tagging.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving firstinformation corresponding to the order data object via a first API for afirst system, where receiving the order data object includes generatingthe order data object based on the first information, and receivingsecond information corresponding to the additional data object via asecond API different from the first API for a second system differentfrom the first system, where receiving the additional data objectincludes generating the additional data object based on the secondinformation.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first field value may berepresented in the first information using a first data format, thesecond field value may be represented in the second information using asecond data format different from the first data format, and the valuemay be represented in the updated order summary data object using thefirst data format, the second data format, or a third data formatdifferent from the first data format and the second data format based onconverting the first data format to a first converted data format forthe order data object, converting the second data format to a secondconverted data format for the additional data object, or both.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting, fordisplay in a user interface, a set of data associated with the ordersummary data object, where the query may be received based on a userinput to the user interface.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting, fordisplay in the user interface, the retrieved value in response to thequery, where the user interface may be updated within a real-time timeconstraint based on retrieving the value directly from the updated ordersummary data object.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the user interface may beassociated with a tenant of the database system, an end-user for thetenant, or both.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the order summary data objectinherits field-based security parameters from the order data object.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving an additionalquery for an additional value corresponding to a third field value atthe order data object, where the additional query includes the orderidentifier, determining that the order summary data object does notinclude the additional value, and retrieving, in response to theadditional query, the additional value from the order data object basedon the order summary data object not including the additional value.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for activating ordersummaries at the database system, identifying an additional order dataobject including an additional order identifier stored at the databasesystem, searching the database system for one or more additional dataobjects associated with the additional order identifier, and building anadditional order summary data object corresponding to the additionalorder identifier based on the additional order data object including theadditional order identifier and the one or more additional data objectsassociated with the additional order identifier.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional data object isan additional order data object, a change order data object, afulfillment order data object, or a return order data object.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional data objectmay be the additional order data object associated with the orderidentifier and the updating includes replacing current order informationfor the order summary data object including first order informationassociated with the order data object with second order informationassociated with the additional order data object, the additional dataobject may be the change order data object associated with the orderidentifier and the updating includes modifying the current orderinformation for the order summary data object from the first orderinformation associated with the order data object based on third orderinformation associated with the change order data object, or theadditional data object may be the fulfillment order data objectassociated with the order identifier or the return order data objectassociated with the order identifier and the updating includes modifyinga current status for at least one item in the order summary data objectbased on the fulfillment order data object or the return order dataobject.

It should be noted that the methods described above describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Furthermore, aspects from two or more of the methods may be combined.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the above description may berepresented by voltages, currents, electromagnetic waves, magneticfields or particles, optical fields or particles, or any combinationthereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of at least one of A, B, or C meansA or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, asused herein, the phrase “based on” shall not be construed as a referenceto a closed set of conditions. For example, an exemplary step that isdescribed as “based on condition A” may be based on both a condition Aand a condition B without departing from the scope of the presentdisclosure. In other words, as used herein, the phrase “based on” shallbe construed in the same manner as the phrase “based at least in parton.”

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media cancomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for data object aggregation at adatabase system, comprising: receiving an order data object comprisingan order identifier; creating an order summary data object based atleast in part on receiving the order data object; receiving anadditional data object associated with the order identifier; updatingthe order summary data object based at least in part on the additionaldata object; receiving a query for a value corresponding to a firstfield value at the order data object and a second field value at theadditional data object, wherein the query comprises the orderidentifier; and retrieving, in response to the query, the value directlyfrom the updated order summary data object based at least in part on theupdated order summary data object comprising information for both theorder data object and the additional data object.
 2. The method of claim1, wherein the order summary data object comprises a current stateassociated with the order identifier, the method further comprising:storing the order summary data object at the database system.
 3. Themethod of claim 2, further comprising: storing the order data object andthe additional data object at the database system, wherein the ordersummary data object comprises a first indicator referencing the orderdata object and a second indicator referencing the additional dataobject.
 4. The method of claim 1, further comprising: determining, uponreceiving the order data object, that the database system does notcurrently store an existing order summary data object corresponding tothe order identifier, wherein the order summary data object is createdbased at least in part on the determining that the database system doesnot currently store the existing order summary data object.
 5. Themethod of claim 4, further comprising: determining, upon receiving theadditional data object, that the database system currently stores theorder summary data object corresponding to the order identifier, whereinthe order summary data object is updated based at least in part on thedetermining that the database system currently stores the order summarydata object.
 6. The method of claim 1, further comprising: generating aninitial value for an aggregate data field of the order summary dataobject based at least in part on the first field value for the orderdata object; and calculating the value for the aggregate data field ofthe order summary data object based at least in part on the second fieldvalue for the additional data object, wherein the value is retrieveddirectly from the updated order summary data object based at least inpart on the calculating.
 7. The method of claim 6, further comprising:receiving a tag for the value; and tagging the aggregate data field withthe tag based at least in part on the order summary data objectcomprising the value for the aggregate data field, wherein the orderdata object and the additional data object do not comprise the value fortagging.
 8. The method of claim 1, further comprising: receiving firstinformation corresponding to the order data object via a firstapplication programming interface (API) for a first system, whereinreceiving the order data object comprises generating the order dataobject based at least in part on the first information; and receivingsecond information corresponding to the additional data object via asecond API different from the first API for a second system differentfrom the first system, wherein receiving the additional data objectcomprises generating the additional data object based at least in parton the second information.
 9. The method of claim 8, wherein: the firstfield value is represented in the first information using a first dataformat; the second field value is represented in the second informationusing a second data format different from the first data format; and thevalue is represented in the updated order summary data object using thefirst data format, the second data format, or a third data formatdifferent from the first data format and the second data format based atleast in part on converting the first data format to a first converteddata format for the order data object, converting the second data formatto a second converted data format for the additional data object, orboth.
 10. The method of claim 1, further comprising: transmitting, fordisplay in a user interface, a set of data associated with the ordersummary data object, wherein the query is received based at least inpart on a user input to the user interface.
 11. The method of claim 10,further comprising: transmitting, for display in the user interface, theretrieved value in response to the query, wherein the user interface isupdated within a real-time time constraint based at least in part onretrieving the value directly from the updated order summary dataobject.
 12. The method of claim 10, wherein the user interface isassociated with a tenant of the database system, an end-user for thetenant, or both.
 13. The method of claim 1, wherein the order summarydata object inherits field-based security parameters from the order dataobject.
 14. The method of claim 1, further comprising: receiving anadditional query for an additional value corresponding to a third fieldvalue at the order data object, wherein the additional query comprisesthe order identifier; determining that the order summary data objectdoes not comprise the additional value; and retrieving, in response tothe additional query, the additional value from the order data objectbased at least in part on the order summary data object not comprisingthe additional value.
 15. The method of claim 1, further comprising:activating order summaries at the database system; identifying anadditional order data object comprising an additional order identifierstored at the database system; searching the database system for one ormore additional data objects associated with the additional orderidentifier; and building an additional order summary data objectcorresponding to the additional order identifier based at least in parton the additional order data object comprising the additional orderidentifier and the one or more additional data objects associated withthe additional order identifier.
 16. The method of claim 1, wherein theadditional data object comprises an additional order data object, achange order data object, a fulfillment order data object, or a returnorder data object.
 17. The method of claim 16, wherein: the additionaldata object comprises the additional order data object associated withthe order identifier and the updating comprises replacing current orderinformation for the order summary data object comprising first orderinformation associated with the order data object with second orderinformation associated with the additional order data object; theadditional data object comprises the change order data object associatedwith the order identifier and the updating comprises modifying thecurrent order information for the order summary data object from thefirst order information associated with the order data object based atleast in part on third order information associated with the changeorder data object; or the additional data object comprises thefulfillment order data object associated with the order identifier orthe return order data object associated with the order identifier andthe updating comprises modifying a current status for at least one itemin the order summary data object based at least in part on thefulfillment order data object or the return order data object.
 18. Anapparatus for data object aggregation at a database system, comprising:a processor; memory coupled with the processor; and instructions storedin the memory and executable by the processor to cause the apparatus to:receive an order data object comprising an order identifier; create anorder summary data object based at least in part on receiving the orderdata object; receive an additional data object associated with the orderidentifier; update the order summary data object based at least in parton the additional data object; receive a query for a value correspondingto a first field value at the order data object and a second field valueat the additional data object, wherein the query comprises the orderidentifier; and retrieve, in response to the query, the value directlyfrom the updated order summary data object based at least in part on theupdated order summary data object comprising information for both theorder data object and the additional data object.
 19. The apparatus ofclaim 18, wherein the order summary data object comprises a currentstate associated with the order identifier, and the instructions arefurther executable by the processor to cause the apparatus to: store theorder summary data object at the database system.
 20. A non-transitorycomputer-readable medium storing code for data object aggregation at adatabase system, the code comprising instructions executable by aprocessor to: receive an order data object comprising an orderidentifier; create an order summary data object based at least in parton receiving the order data object; receive an additional data objectassociated with the order identifier; update the order summary dataobject based at least in part on the additional data object; receive aquery for a value corresponding to a first field value at the order dataobject and a second field value at the additional data object, whereinthe query comprises the order identifier; and retrieve, in response tothe query, the value directly from the updated order summary data objectbased at least in part on the updated order summary data objectcomprising information for both the order data object and the additionaldata object.